Downloading a Code Image to Remote Devices

ABSTRACT

A server downloads a code image to remote devices so that the remote devices are performing properly in accordance with an updated version of the code image. The server may include an application server that targets devices and informs the targeted devices about a multicasting session. The targeted devices subsequently join the multicast session supported by a multicasting server and extract the code image from the multicast session. After the multicast session has been completed, the downloading center polls the targeted devices to determine which devices have successfully downloaded the code image. The server may repeat the download to devices that did not successfully download the code image by subsequently scheduling a subsequent multicasting session or by individually sending the code image to the devices. Portions of the code image may be sent in multicasting messages based on a depth level and interval.

TECHNICAL FIELD

Aspects of the disclosure relate to downloading a code image to remote devices.

BACKGROUND

Content transmission and communication systems, e.g., high speed data and television content transmission systems, serve numerous users (often many thousands), in which each user has one or more devices (e.g., display devices, gateways, set top boxes or modems) to process signals at the user's premise. These devices often contain sophisticated software having very large code images that may be changed in order to provide new services and to enhance existing services. Downloading code images from a central facility to devices in the field may thus require a large investment in servers and cause a substantial increase of network congestion over a significant period of time in order to transmit a large amount of information. The time to deliver a code image may take several hours depending on the scheduling over a large network. If downloading to a device is not successful, a subsequent complete or partial download is scheduled. The complexity of the downloading process is further compounded by the large number of devices that may be involved. Consequently, the downloading process may result in a substantial amount of resources being diverted from other network needs.

BRIEF SUMMARY

The following presents a simplified summary of the disclosure in order to provide a basic understanding of some aspects. It is not intended to identify key or critical elements of the disclosure or to delineate the scope of the disclosure. The following summary merely presents some concepts of the disclosure in a simplified form as a prelude to the more detailed description provided below.

A server downloads a code image to remote devices so, for example, a the remote devices are performing in accordance with an updated version. The server may be an application server that targets devices and informs the targeted devices about a multicasting session that is supported by a multicasting server. The targeted devices subsequently join the multicast session and extract the code image from the multicast session. After the multicast session has been completed, the downloading center may poll the targeted devices to determine which devices have successfully downloaded the code image. The downloading center may download the code image to devices that did not successfully download the code image by subsequently scheduling a subsequent multicasting session or by individually sending the code image to the devices. The downloading center may determine whether to reschedule a multicasting session or whether to use unicast transmission based on a percentage of devices that have successfully downloaded the code image.

In another aspect of the disclosure, a code image may be sent in multicast messages based on a depth level and interval, where the depth level sets the size of a transmitted portion of the code image and the interval sets the number of repeats for transmitting each portion. The depth level and the interval may be set to predetermined values or may be dynamically determined based on a transmission metric.

Other embodiments can be partially or wholly implemented on a computer-readable medium, for example, by storing computer-executable instructions or modules, or by utilizing computer-readable data structures.

Of course, the methods and systems of the above-referenced embodiments may also include other additional elements, steps, computer-executable instructions, or computer-readable data structures. In this regard, other embodiments are disclosed and claimed herein as well.

The details of these and other embodiments are set forth in the accompanying drawings and the description below. Other features and advantages of the disclosure will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which:

FIG. 1 shows an application manager in accordance with various aspects of the disclosure.

FIG. 2 shows a flow diagram for a procedure for downloading code images in accordance with aspects of the disclosure.

FIG. 3 shows a multicast server that supports downloading an image in accordance with aspects of the disclosure.

FIG. 4 shows a process for downloading an image to devices in accordance with various aspects of the disclosure.

FIG. 5 shows a flow diagram for downloading an image to devices in accordance with aspects of the disclosure.

FIG. 6 shows a flow diagram for supporting a multicast session in accordance with aspects of the disclosure.

FIG. 7 shows an apparatus that supports downloading a code image in accordance with aspects of the disclosure.

FIG. 8 shows an apparatus that supports downloading a code image in accordance with aspects of the disclosure.

DETAILED DESCRIPTION

Traditional systems may download a code image (e.g., a stored representation of instructions that may be executed) to a remote device by transmitting a file in a data carousel using a multicast stream (e.g., broadcast method). Other traditional systems may use a file transfer protocol (FTP) to send a file to the remote device (e.g., unicast method). One known protocol is trivial file transfer protocol (TFTP), which typically uses a small file transfer size (typically less than 1 Mbyte). The broadcast method is typically proprietary per vendor implementation and is not standardized. However, while the unicast method may be standardized, it often results in substantial network congestion.

Aspects of the disclosure enable the time to upgrade a large network of devices to be reduced. In contrast, for example, it may require six to twelve months to complete firmware upgrades for a television content transmission system having a total population with millions of subscribers. Consequently, the potential for saving time and resources is substantial for network upgrades.

FIG. 1 shows system 100 in which downloading center 104 transmits an updated code image to remote devices for use, such as execution. As shown in FIG. 1, downloading center 104 includes application manager 103 and server 101, which may be a multicast server. Application manager (AM) 103 targets network endpoint devices 105-110 (e.g., display devices, mobile devices, gateways, set-top boxes (STBs), cable modems (CMs), cable modem termination systems (CMTSs), and routers) for downloading and subsequently may instruct devices 105-110 to join a multicast session in accordance with various aspects of the disclosure. (While the example shown in FIGS. 1 and 2 only depict downloading to devices 105, 107, and 109, embodiments typically support downloading a code image to hundreds or even thousands of devices during a multicast session.) Application manager 103 directs server 101 to download the code image in a multicast session as shown in FIG. 2 as discussed below. Referencing FIG. 1 server 101 accesses the code image in order to transmit the multicast session stream through Internet Protocol (IP) network 150. In the embodiment shown in FIG. 1, for example, IP network 150 may comprise one or more regional networks.

In order to establish a multicast session, application manager 103 may send unicast messages (e.g., using Simple Network Management Protocol (SNMP)) to targeted devices 105, 107, and 109 over communication lines 151, 153, and 155, respectively. The messages may be sent through a network 150, such as a wired or wireless IP network 150, termination systems 111 and 113, and networks 160 and 170 in order to instruct devices 105, 107, and 109 to join that multicast session as will be further discussed with FIG. 2. According to some embodiments, networks 160 and 170 may comprise fiber optic, coaxial cable, wireless, satellite, or hybrid fiber coaxial (HFC) networks, which may support Internet Protocol (IP) or any other protocol. Networks 160 and 170 may be extensions of IP network 150. Application manager 103 may select the targeted device using different criteria. For example, a download session may target a particular device model that is concentrated in a geographical location. As another example, devices may be dispersed across different markets in order to balance the traffic during the download process so that any particular network is not excessively congested from the download.

System 100 may utilize a wireless communication channel in lieu of or in conjunction with a wired network to communicate with devices 105, 107, and 109.

Application manager 103 subsequently may inform multicast server 101 to transmit the code image to devices 105, 107, and 109 in the multicast session. After the download has completed for the multicast session, application manager 103 may poll devices 105, 107, and 109 to determine which devices have been successfully upgraded, for example. Application manager 103 may determine when to poll based on different criteria, including a predetermined time or a download session completion acknowledgment from multicast server 101.

In the example shown in FIG. 1, the remaining devices (e.g., devices 106, 108, and 110) may be provided with the code image in one or more separate multicast sessions. Also, while not shown explicitly, multicast server 101 may comprise one or more servers.

FIG. 2 shows flow diagram 200 for a procedure for downloading code images to network endpoint devices in accordance with aspects of the disclosure. In step 201, targeted network endpoint devices are selected. In step 203, the code image is transmitted to the targeted devices. In some embodiments, the targeted device may join a multicast session, in which the code image is transmitted to the targeted devices. In other embodiments, the network endpoint devices may be notified of a broadcast session, which does not require that the targeted device join a multicast group. Rather than exchanging multicast messaging between an endpoint device and a server, the network endpoint device may listen to the broadcast at the scheduled time as indicated in schedule information contained in a transmitted notification table from the server.

In step 205, each targeted devices may be polled to verify that the download was successful for the device. If not, the download can be repeated in step 207 by retransmitting the code image to the device. For example, the device can join a subsequent multicast session or the code image can be sent through unicast (direct) messaging.

Referring to FIG. 3, multicast server 101 supports multicast session 351 through routers 301 and 303 and termination systems 111 and 113 for downloading a code image to devices 105, 107, and 109 in accordance with aspects of the disclosure. With some embodiments of the disclosure, multicast server 101 starts a multicast stream. Consequently, targeted devices 105, 107, and 109 join the multicast group using an appropriate protocol such as Internet Group Management Protocol (IGMP). Multicast server 101 then uses an IP multicast group to send the content of the code image, in which the group address provides the IP destination address in data packets. Devices 105, 107, and 109 use this group address to inform the network that they are interested in receiving packets that contain code image updates sent to that group. Multicast server 101 then downloads the code image by partitioning the code image and delivering the partitions using, for example, data packets (e.g., with User Datagram Protocol (UDP) or Transmission Control Protocol (TCP)).

FIG. 4 shows process 400 for downloading image code to targeted devices in accordance with various aspects of the disclosure. For example, process 400 may use a data structure that maps IP addresses to network endpoint devices in order to identify targeted devices. In step 401, application manager 103 identifies devices (e.g., display devices, mobile devices, gateways, set-top boxes 105, 107, and 109) for downloading and instructs the identified devices to join the multicast session that is subsequently initiated by multicast server 101. The multicast session is consequently configured by the targeted devices joining the multicast group. In step 403, multicast server 101 sends the content of the image code to the targeted devices using a multicast protocol, which may run on top of the user datagram protocol.

As will be discussed in further detail, the download status of the targeted devices is determined in step 405. Based on the download status, the code image may be separately downloaded to selected devices in step 407, or a subsequent multicast session may be scheduled for some or all of the targeted devices that did not successfully download the code image. Typically, the number (M) of devices that are separately downloaded is substantially smaller than the number (N) of devices that were previously downloaded in the previous multicast session so that the resulting traffic does not result in traffic congestion.

As discussed above, a targeted device may join a multicast group in order to receive the code image content. If the targeted device does not successfully download the code image based on a predetermined criterion, server 101 may directly communicate only with the targeted device using unicast messages. Moreover, with some embodiments a device may obtain code image content by receiving a broadcast transmission without joining a multicast group.

FIG. 5 shows flow diagram 500 for downloading a code image to targeted devices in accordance with aspects of the disclosure. In step 501, application manager 103, determines the targeted devices and instructs those devices to join the multicast session (stream) that multicast server 101 is sending. In step 503, and as further discussed with FIG. 6, multicast server 503 sends multicast messages in the multicast stream to provide the code image to devices that joined the multicast session. In step 505, a targeted device processes (digests) the content of multicast messages to extract the code image. If the targeted device does not accept the code image in step 507, the device indicates so with a status indicator. For example, with some embodiments, the device sets a readable object such as a SNMP object to indicate the downloading status of the device. For example, Internet Engineering Task Group RFC 2669 (DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems) specifies a procedure docsDevSwAdminStatus having a value equal to 1, 2, or 3 corresponding to “upgradeFromMgt”, “allowProvisioningUpgrade”, or “ignoreProvisioningUpgrade”, respectively, to indicate the downloading status of the device. If a device has successfully received a code image, the device sets the object value to “ignoreProvisioningUpgrade.” The device verifies the code image in step 409.

In step 511, after a predetermined time has expired, application server 103 polls the targeted devices to verify receipt of the code image upgrade. However, while the code image may be upgraded, some embodiments may download other versions of the code image. If all of the targeted devices successfully downloaded the code image, as determined by step 513, downloading process 500 terminates at step 519. Otherwise, step 515 determines whether at least a predetermined percentage of targeted devices successfully downloaded the code image. If not, a subsequent multicast session is scheduled for the devices that did not successfully download in the multicast session. However, if at least a predetermined percentage of the targeted devices successfully downloaded the code image, in step 417 application server 103 individually sends the code image to each device that did not successfully download in the multicast session using unicasting (e.g., TFTP or HTTP).

FIG. 6 shows a flow diagram for supporting multicast session 500 (corresponding to step 503 as shown in FIG. 5) in accordance with aspects of the disclosure. In step 601, multicasting server 101 initiates the multicast stream that contains the code image. The size of each portion is configured by the amount of code image content (depth) contained in each set of packets in step 603. Each portion of the code image is transmitted in the multicast stream in step 605. The depth may correspond to a number of packets containing a corresponding number of bytes, where the portion is repeated a number of times as determined by the interval. For example, if the interval is equal to 5, then a targeted device may have five chances to obtain a code image portion. When a portion has been repeated the configured number of times, multicast server 101 sends the next portion in step 609 until the complete code image has been transmitted as determined by step 607.

Process 600 further repeats the transmission of the complete code image, each corresponding to a carousel try in steps 613 and 611, where a carousel try corresponds to a repeat of the code image content in the transmitted data carousel. When all of the carousel tries have been completed, the multicast phase is terminated (corresponding to the completion of step 615).

The depth and interval may be set to predetermined values in process 503. However, with some embodiments, the depth and interval (determined in step 603) may be dynamically configured based on a transmission metric that is indicative of the communications conditions between multicasting server 101 and the targeted devices. For example, system 100 may utilize a monitoring device (not explicitly shown) that monitors a transmission metric (e.g., the error rate of the received communication signal) from multicasting server 101. Multicasting server 101 may consequently adjust the depth and interval (as shown in FIG. 6) based on the transmission metric during the multicast session. With some embodiments, devices 105, 107, and 109 may have monitoring capabilities for determining a transmission metric and for informing downloading center 104 about the transmission metric.

In some embodiments, devices 105, 107, and 109 provide a download status that is indicative of a percentage of the code image that was successfully downloaded to the device. For example, if a device could not download a portion of the code image during the multicast session, the device may cease downloading any subsequent portions of the code image during the multicast session. If the percentage exceeds a percentage threshold, downloading center 104 may subsequently download the remaining part of the code image in a unicast transmission to the device.

FIG. 7 shows apparatus 700 that supports downloading a code image to a network endpoint device in accordance with aspects of the disclosure. With some embodiments, apparatus 700 supports the functionalities of application manager 103 and multicast server 101 as shown in FIGS. 1 and 2. Processor 701 may execute computer executable instructions from a computer-readable medium, e.g., memory 709 in order perform a data transmission process (any or all of the transmission processes described herein). Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media include, but is not limited to, random access memory (RAM), read only memory (ROM), electronically erasable programmable read only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by processor 701. The executable instructions may carry out any or all of the method steps described herein. With some embodiments, processor 701 may comprises one or more processing devices.

Memory 707 stores one or more versions of the image code for downloading to network endpoint devices, e.g., devices 105, 107, and 109.

Processor 701 performs the functionalities of application server 103 by sending unicast messages (e.g., SNMP and TFTP) through unicast interface 705 through converged regional network 150 and hybrid fiber cable networks 160 and 170. Processor 701 performs the functionalities of multicasting server 101 by sending multicasting messages through multicast interface 703 through networks 150, 160, and 170 in order to download the code image into devices 105, 107, and 109.

FIG. 8 shows apparatus 800 that supports downloading a code image at a network endpoint device in accordance with aspects of the disclosure. With some embodiments, apparatus 800 supports the functionalities of devices 105 and 107 as shown in FIGS. 1 and 2. Processor 801 may execute computer executable instructions from a computer-readable medium, e.g., memory 807 in order perform a data transmission process (any or all of the transmission processes described herein). Memory 805 stores one or more versions of the image code that has been downloaded from multicast server 101.

Processor 801 performs the functionalities of a network endpoint device by receiving unicast (direct) messages (e.g., SNMP and TFTP) through network interface 803. Processor 801 also receives multicast messages through network interface 803 in order to download the code image to memory 805.

While the exemplary embodiments have been discussed in broad terms of a cable communications networking environment, the disclosure may be configured for other networking environments including telecommunications environments. 

1. A method, comprising: sending, in a first multicast session, a file to a plurality of devices; for each of the plurality of devices, determining whether the device successfully received the file during the first multicast session; and performing, by at least one computing device, one of the following depending upon which of the plurality of devices are determined to have successfully received the file during the first multicast session: sending, in a second multicast session, the file to a subset of the plurality of devices, or sending, for each of the subset of the plurality of devices, the file in a unicast session with the respective one of the plurality of devices.
 2. The method of claim 1, wherein the file comprises a code image.
 3. The method of claim 1, wherein said sending the file in the second multicast session comprises setting up the second multicast session.
 4. The method of claim 1, further comprising determining how many of the plurality of devices successfully receive the file, wherein said performing comprises performing, by the at least one computing device, said one of the following depending upon how many of the plurality of devices are determined to have successfully received the file during the first multicast session.
 5. The method of claim 1, further comprising determining a percentage of the plurality of devices successfully receive the file, wherein said performing comprises performing, by the at least one computing device, said one of the following depending the percentage of the plurality of devices determined to have successfully received the file during the first multicast session.
 6. The method of claim 1, wherein for each of the subset of the plurality of devices, the unicast session is separate from the unicast sessions of remaining ones of the subset of the plurality of devices.
 7. The method of claim 1, wherein said determining comprises receiving a message from each of at least some of the plurality of devices, each of the messages indicating whether a particular one of the plurality of devices successfully received the file during the first multicast session.
 8. The method of claim 1, further comprising polling the plurality of devices, wherein said determining is performed based on responses to the polling.
 9. The method of claim 1, wherein if an insufficient quantity of the plurality of devices are determined to have successfully downloaded the file, then said performing comprises said sending, in the second multicast session, the file to the subset of the plurality of devices.
 10. The method of claim 1, wherein if at least a sufficient quantity of the plurality of devices are determined to have successfully downloaded the file, then said performing comprises said sending, for each of the subset of the plurality of devices, the file in the unicast session with the respective one of the plurality of devices.
 11. A method, comprising: sending a file to a plurality of devices including a first device during a multicast session; determining, by at least one computing device, a status of at least some of the plurality of devices; and depending upon whether the status is indicative that the file successfully received more than a predetermined portion of the plurality of devices during the multicast session and that the first device did not successfully receive the file, selectively sending the file to the first device.
 12. The method of claim 11, further comprising: responsive to determining that less than the predetermined portion of the plurality of devices successfully received the file, scheduling a subsequent multicast session and sending the file to at least some of the plurality of devices during the subsequent multicast session.
 13. The method of claim 11, wherein said determining the status comprises comparing a portion of the plurality of devices that successfully received the file with the predetermined portion, and wherein said selectively sending is selectively performed depending upon an outcome of said comparing.
 14. The method of claim 11, wherein said sending comprises sending the file to the device during a unicast session with the device.
 15. The method of claim 11, wherein the predetermined portion is a predetermined percentage.
 16. A method, comprising: sending a file to a plurality of devices during a multicast session; and performing, by at least one computing device, the following: responsive to determining that the file successfully downloaded to more than a predetermined portion of the plurality of devices during the multicast session and that a first device of the plurality of devices did not successfully download the file, sending the file to the first device, or responsive to determining that less than the predetermined portion of the plurality of devices successfully downloaded the file, scheduling a subsequent multicast session and sending the file to at least some of the plurality of devices during the subsequent multicast session.
 17. The method of claim 16, wherein said sending the file to the first device comprises transmitting the file to the first device during a unicast session with the first device.
 18. The method of claim 16, wherein the file comprises a code image.
 19. The method of claim 16, wherein said determining comprises comparing a portion of the plurality of devices that successfully downloaded the file with the predetermined portion.
 20. The method of claim 16, wherein said sending the file to the plurality of devices comprises: determining a depth level and an interval value; sending a portion of the file based on the depth level; and repeating sending, to the plurality of devices, the portion a number of times that is based on the interval value. 